-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IBX-8891: Fixed XML link validation to allow using tel:
in links
#245
IBX-8891: Fixed XML link validation to allow using tel:
in links
#245
Conversation
d0a170a
to
20ba45e
Compare
tel:
in links
- | ||
message: "#^Offset 1 does not exist on array\\{0\\?\\: string, 1\\?\\: ''\\|'ezremote\\://', 2\\?\\: string, 3\\?\\: string\\}\\.$#" | ||
count: 1 | ||
path: src/lib/eZ/FieldType/RichText/RichTextStorage.php |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: allowing this since this is baseline alignment after an update and fixing this requires some changes that would take significant amount of time (impl + QA)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, and the same thing was done in 4.6 : ibexa/fieldtype-richtext@560eecf
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
QA approved on IbexaDXP 3.3 commerce.
Description:
Adds supports for
tel:
linksI synced with Gunnstein and we agree to keep the validation in schematron, but to simplify it, in order to keep the number of checks down as there is a default limit of 9:
The most important think in this case is to ensure the security aspect, not to ensure that the URLs are syntactical correct (ie, we don't need to check for
ezcontent://
,ezlocation://
,ezremote://
orezurl://
. We can simply have one rule that check for "starts with ez")You may have a look at #244 for a different approach